-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate all iOS and Android precheck actions #577
Conversation
end | ||
|
||
def self.deprecated_notes | ||
'This action is deprecated and will be removed in an upcoming Release Toolkit version. Any necessary steps that are included in this precheck action should be added directly in a repo\'s Fastfile. See https://github.com/wordpress-mobile/release-toolkit/issues/576' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick.
'This action is deprecated and will be removed in an upcoming Release Toolkit version. Any necessary steps that are included in this precheck action should be added directly in a repo\'s Fastfile. See https://github.com/wordpress-mobile/release-toolkit/issues/576' | |
'This action is deprecated and will be removed in the next major version Release Toolkit update. Any necessary steps that are included in this precheck action should be added directly in a repo\'s Fastfile. See https://github.com/wordpress-mobile/release-toolkit/issues/576' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed in a27ec90
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @spencertransier .
Great timing 😄
def self.description | ||
'Runs some prechecks before preparing for a new test build' | ||
'(DEPRECATED) Runs some prechecks before preparing for a new test build' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Removed in 8d87d87
What does it do?
Fixes #576
This PR deprecates the following precheck actions:
android_betabuild_prechecks
android_build_prechecks
android_codefreeze_prechecks
android_completecodefreeze_prechecks
android_finalize_prechecks
android_hotfix_prechecks
ios_betabuild_prechecks
ios_build_prechecks
ios_codefreeze_prechecks
ios_completecodefreeze_prechecks
ios_finalize_prechecks
ios_hotfix_prechecks
When the versioning changes were added in #512, it was decided that we would stop using these
-prechecks
actions and instead use any necessary steps from those actions directly in Fastfiles. The idea is that the precheck actions were opaque and made it harder to figure out where errors were occuring when running release management lanes. There are some other versioning and preflight actions that we'll want to deprecate as well (at least the versioning ones for sure), but I decided to limit this PR to only the precheck actions.Example: See these WooCommerce iOS and Android PRs that switched from using the precheck actions to directly adding the steps in the Woo lanes:
From what I can tell, the Simplenote Android, iOS, and Mac apps are the only apps still using these prechecks (they weren't updated with the versioning changes last year), so it won't be a lot of work for us once these actions are eventually removed.
Checklist before requesting a review
bundle exec rubocop
to test for code style violations and recommendationsspecs/*_spec.rb
) if applicablebundle exec rspec
to run the whole test suite and ensure all your tests passCHANGELOG.md
file to describe your changes under the appropriate existing###
subsection of the existing## Trunk
section.MIGRATION.md
file to describe how the changes will affect the migration from the previous major version and what the clients will need to change and consider.